perm filename REMPU.SPC[CMS,LCS] blob
sn#284238 filedate 1977-05-19 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002 SPECS FOR MICROPROCESSOR SYSTEM FOR REM
C00007 ENDMK
C⊗;
SPECS FOR MICROPROCESSOR SYSTEM FOR REM
Munged by LCS, May 19
This edition, 1977.May.12 13 PDT
HARDWARE SPECS:
Cabinet: black-box with power-cord, two RS-232 sockets, on/off
switch, reset and interupt push buttons.
Power supply: 117 volts 60 Hertz input. +5 (-12 maybe) output.
(It might not be worth the bucks for a big supply until
you accualy add the extras).
CPU board: CPU, power fail/start, bus buffers, EPROM (2*256*8 ∨ 1k*8).
Memory (RAM) board: 4k*8 bufferd and decoded.
I/O board: 2 RS-232 ports, 4 or 8 chanel programable bit-rate generator.
I/O extra: room in box for 3 spare IObus cards added later if you want to
include cassette, Holofile, auto-dial-auto-answer controllers interfaces
whatever.
SOFTWARE:
PROM already programmed with rudimentary octal or
hexidecimal debugger like ddt, with all of the following
working: 1) Type in number to specify address 2) Type out
contents 3) Type in contents to replace old data 4) Step
foreward in memory addressing space 5) Step backward similar
6) Jump indirect (or similar) through some location to start program.
This debugger would work from the first RS-232 port.
RESET-START or whatever (reset button) on physical control
panel would restart DDT.
Saving PC etc. on stack followed by start ddt would
happen when either of these two conditions happend: (a) special
instruction executed (b) special physical interrupt button on console pressed.
DOCUMENTATION:
Prints for all circuitry (not necessarily formal high
quality professional prints, just copies of what you used
to design it so I can figure out how it's all put together).
Listings of all software
provided. Instructions for how to avoid burning out things
(like how to power-down before pulling or inserting a card).
END.